Draft
Conversation
…rors) Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update OpenTelemetry SDK and instrumentation versions
Upgrade OpenTelemetry to 1.58.0 / 2.24.0
Jan 28, 2026
Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
Copilot
AI
changed the title
Upgrade OpenTelemetry to 1.58.0 / 2.24.0
Add system property fallback to DeclarativeConfigUtil config access
Jan 28, 2026
Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
After OpenTelemetry upgrade to 2.24.0, GlobalOpenTelemetry.getPropagators() doesn't work correctly in test environments. Changed to use W3CTraceContextPropagator.getInstance() directly for context extraction. Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
Copilot
AI
changed the title
Add system property fallback to DeclarativeConfigUtil config access
Fix Azure Functions context propagation after OpenTelemetry 2.24.0 upgrade
Feb 4, 2026
Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
The upstream OpenTelemetry javaagent already includes io.opentelemetry.common classes (properly shaded). Our build was including the same classes, causing classloader conflicts. Added exclusion to prevent double inclusion. Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
Copilot
AI
changed the title
Fix Azure Functions context propagation after OpenTelemetry 2.24.0 upgrade
Upgrade OpenTelemetry to 1.58.0 / 2.24.0
Feb 5, 2026
AiConfigCustomizer properties need to be accessible by instrumentation modules that load early. Setting them as system properties ensures they're available through the System.getProperty() fallback mechanism. Co-authored-by: xiang17 <9310587+xiang17@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrades OpenTelemetry SDK from 1.55.0 to 1.58.0 and Instrumentation from 2.21.0 to 2.24.0. The upgrade introduced breaking internal API changes and a new
io.opentelemetry.commonpackage that required build and configuration fixes.Breaking API Changes
AgentInstrumentationConfig removal
Upstream removed the internal config API. Migrated to
DeclarativeConfigUtilwith system property fallback:LoggingCustomizer interface
Method signature changed from
init(EarlyInitAgentConfig)toinit().Context propagation
GlobalOpenTelemetry.getPropagators()unreliable in test environments. Azure Functions instrumentation now usesW3CTraceContextPropagator.getInstance()directly.Build Fixes
LinkageError resolution
The new
io.opentelemetry:opentelemetry-commondependency was included both from upstream javaagent (already shaded) and our dependencies, causing loader constraint violations. Excluded from our javaagent libs:dependencies { exclude(dependency("io.opentelemetry:opentelemetry-common")) }Double relocation prevention
Added exclusions in shadow conventions to skip classes already shaded by upstream (
io.opentelemetry.javaagent.shaded.*).Configuration Timing Fix
Instrumentation modules load before
AiConfigCustomizerruns. Properties from the customizer (custom instrumentation, micrometer config) must also be set as system properties for early access:Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.